Method and system to process payment

ABSTRACT

Provided is a method and system for payment processing, including emailing a billing statement including an online payment hyperlink to a payer by a biller. The online payment hyperlink includes a payer personalized URL and a token uniquely identifying the payer. The online payment hyperlink is selected by the payer, who is then presented with the biller&#39;s online payment form, including pre-populated data fields. The biller&#39;s online payment form is reviewed, completed and corrected by the payer, and sent to a secure payment form server.

FIELD OF THE INVENTION

This invention generally relates to a method and system of payment processing, and, more particularly, to a method and system of encouraging electronic payments by providing a personalized hyperlink containing a token that identifies a payer and a corresponding reference to stored account information.

BACKGROUND OF THE INVENTION

Many payments, such as but not limited to those for child care, donation pledge commitments, membership renewals and other types of non-profit financial transactions are presently still made by check. Current processes of billing for and collecting such payments are often inconvenient, for both the payer and the collecting organization. Attempts to introduce more automated means of payments, such as preauthorized credit card and direct bank debit (ACH) payments, have had limited success due at least in part to the reluctance of payers to trust and agree to such methods.

Many systems for online payment require payers to login to an online system to display charges and make payment. This requires payers to register, remember login information and generally reduces the likelihood that payers will utilize such a system. Other systems that don't require a login typically require the user to enter all of the data each time they wish to make a payment. Entry of data each time increases the likelihood of entry error. Errors in entry may incur extra costs for declined or unsuccessful transactions and increase payer frustration. Entry errors are especially problematic for ACH payments where there is currently no system for real-time validation of the account information entered, and where the necessary bank routing and account numbers are potentially difficult for the payer to be certain of.

Thus, there is a need to adapt numerous new and evolving technologies to provide a much simpler method of allowing payers to initiate one-time and recurring payments by credit card or ACH payment with a minimum of effort. This method would also increase payer confidence so that organizations could encourage payers to more readily sign-up and transition to preauthorized collection of payments due.

SUMMARY OF THE INVENTION

An aspect of the present invention provides a payment processing method and system, including emailing a billing statement to a payer by a biller, the billing statement including an online payment hyperlink. The online payment hyperlink includes a URL personalized for the payer and a token uniquely identifying the payer, as well as other data, such as amount due and data to facilitate proper posting, such as accounting codes. The online payment hyperlink is then selected by the payer, who is then presented with the biller's online payment form. The online payment form includes data fields pre-populated with available payer information included in the link or stored and associated with the payer token. The biller's online payment form is then reviewed by the payer, who completes and corrects the data as needed. The completed online payment form is then sent to a secure payment form server by the payer.

In one aspect of the invention, the payer payment data is transmitted to an online payment gateway by the secure payment form server, and payment is processed by the online payment gateway.

In another aspect of the invention, the online payment gateway's payment processing includes accessing a secure data vault to obtain payer payment information, transmitting payer payment information to a credit/debit card network, receiving a transaction record from the credit/debit card network, updating the form server data vault with the transaction record information, and updating the payer's stored information in the secure data vault.

In one aspect of the invention, the payer is presented with an option to authorize saving payment data to a hosted secure server, the payer then authorizes the saving of payment data, and the data is saved to a secure data vault.

In another aspect of the invention, the payer is presented with an option to authorize automatic recurring payments to the biller, and authorizes such payments. This aspect of the invention includes a method for recording an electronic signature of authorization.

In one aspect of the invention, the biller may request email payment notices be sent to the biller's organizational contact and/or to the payer. With this option, an email notice is sent to biller's organizational contact and/or the payer upon payment completion.

Another aspect of the invention includes the biller's organizational contact logging into the hosted secure form server and downloading the completed transaction records.

In another aspect of the invention, the biller may process additional one-time payments initiated in person or by phone utilizing the same payer token to reduce data entry and speed payment processing.

In another aspect of the invention, certain data such as the biller specified G/L accounting codes, unique payer identifier, etc. are passed to the payment form but not displayed. This allows them to be recorded as part of the payment transaction to facilitate better handling of the data when imported back into the organization's accounting system.

In another aspect of the invention, the online payment forms are easily customized to include the billing organization's logo, website color scheme, instructions, security graphics, and other elements to ensure payer confidence in providing sensitive credit card or bank account data.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a schematic diagram illustrating a payment processing system, in accordance with an embodiment of the present invention;

FIG. 2( a) is a flowchart depicting a method of payment processing, in accordance with an embodiment of the present invention;

FIG. 2( b) is a flowchart depicting a method of payment processing, in accordance with an embodiment of the present invention;

FIG. 3 is a flowchart depicting a method of payment processing including optional authorization of saving payment data, in accordance with an embodiment of the present invention;

FIG. 4( a) is a flowchart depicting a method of payment processing including provision of email payment notices, in accordance with an embodiment of the present invention; and

FIG. 4( b) is a flowchart depicting a method of payment processing including downloading of completed transaction records by a biller's organizational contact, in accordance with an embodiment of the present invention.

DETAILED DESCRIPTION

In the following description, for purposes of explanation, specific numbers, materials and configurations are set forth in order to provide a thorough understanding of the invention. It will be apparent, however, to one having ordinary skill in the art, that the invention may be practiced without these specific details. In some instances, well-known features may be omitted or simplified so as not to obscure the present invention. Furthermore, reference in the specification to “one embodiment” or “an embodiment” means that a particular feature, structure or characteristic described in connection with the embodiment is included in at least one embodiment of the invention. The appearances of the phrase “in an embodiment” in various places in the specification are not necessarily all referring to the same embodiment.

The term “payer” referred to in the descriptions of various embodiments of the invention herein described is intended to generally describe any person or company having a need or desire to make a payment to any biller, without limitation. Typically, a payer is a private individual, but it may alternatively be a public or private entity, such as a company, partnership or corporation.

As used herein, the term “biller” refers to any entity desiring to solicit payment from any payer, without limitation. Examples of billers are charities, service providers, retail and wholesale businesses, utilities, etc.

As used herein, the terms “computer” or “computer system” refers to any commonly used computer device having at least a processor, associated memory, and one or more input device, without limitation. The computer may be within the biller's office, or one used or accessed remotely to host the biller's accounting applications. Examples of computers include, but are not limited to, desktop computers, laptop computers, minicomputers, mobile devices, cellular telephones, and others. It is assumed all computers described herein incorporate an appropriate operating system, any additional necessary software and any necessary communication interfaces.

The term “credit card”, as used herein in connection with systems, networks or transactions, is understood to include other similar systems and transactions clearly and expressly limited in scope. Thus, a description including the use of ‘credit card processing network’ includes debit card processing networks as well as electronic check processing networks (ACH).

Similarly, communication between system elements, for example, in figure item nos. 120, 122, 124, 126, 128, 130, 132, 134, 136, and 138, is assumed to be over conventional communication lines and interfaces, without limitation.

The present invention advantageously provides a streamlined payment process and system allowing payers to authorize payments without needing to login, thereby eliminating the need for the payer to remember a user id and password. It also advantageously provides for minimizing the data that must be entered by the payer to make a payment.

The present invention also advantageously provides for billers and payers to be assured that their correct balance due or donation amount is paid.

The present invention also advantageously provides for secure storage of payer account data for both credit and debit cards and ACH.

The present invention also advantageously provides a save process and authorization form to encourage preauthorized recurring payments or donations.

The present invention also advantageously provides a method of handling credit card data that meets credit card security standards, such as PCI and CISP standards.

The present invention also advantageously provides a method of uniquely identifying the payer so that a completed payment transaction can be automatically associated with the correct payer account including any desired payment or accounting classification.

FIG. 1 depicts an exemplary payment processing system 100. In an embodiment of the invention, a biller's computer 104 sends an emailed invoice 101 to the payer's computer 106. It is understood that biller's computer 104 and payer's computer 106 may be any type of computer system, including personal computers and even other electronic devices enabled to communicate with other systems. Transmission 122, 120 of the emailed invoice from the biller's computer 104 to the payer's computer 106 also may be by any common communication interface, such as via Internet email.

The emailed invoice 101 preferably includes a “pay online” hyperlink 102, with a personalized URL including a “token” or other data that uniquely identifies the payer, not depicted. The “token” or other data may include any information and is intended to pre-populate the online payment form fields and provide a key for obtaining stored payer information. The hyperlink 102 may also include data such as the biller's desired general ledger accounting code for the payments.

Also in an embodiment, when the payer selects the “pay online” hyperlink, a payment form 108 is provided having some or all fields of the form 108 pre-populated by a secure payment form server 110. The degree of pre-population of the payment form 108 is determined by the amount of payer information available as part of the URL, from previous transactions, or stored in the secure data vault accounting with the token.

The payer then may review the pre-populated data on the payment form 108, correct, update, and/or add missing information. At this point, the payer can enter payment information onto the payment form 108, such as credit card, debit card, bank account or other payment information. As discussed further below, in an embodiment of the invention, the payer's payment information may have already been provided in the pre-populated payment form 108 by the secure payment form server 110, if the payer had previously approved storing of the data.

Once the payment form 108 has been reviewed and, if necessary, corrected or completed by the payer to include payment method information, the payer can submit the payment form 108 via the secure payment form server 110, with the payment or card data 130 and other information being sent to an online payment gateway 112, and thereon onto a credit or debit card network 116, direct debit (ACH) network 118 or other payment processing network (not depicted), as appropriate. The online payment gateway 112 is also communicatively connected 134 with a secure data vault 114, which may be used to record payment processing information.

In a preferred embodiment of the invention, a browser redirect technique is used whenever payment information is to be collected so that data is being entered directly on the gateway payment server rather than the form server. In this way the form server never directly processes or transmits the card data, thus eliminating a potential point of PCI (“Payment Card Industry”) compliance failure.

Once the payment has been processed by the online payment gateway 112, a transaction record and an updated account “token” or other data is passed 132 back to the secure payment form server 110, from which the processed transaction information is downloaded 126 by the biller's computer 104. This updated account token or other data is also used by the secure payment form server to provide subsequent pre-populated information for the payment form 108 when needed. The token data stored in the biller's computer and associated with a particular payer can also be used by a recurring billing system and/or by a “virtual terminal” for additional one-time staff-processed payments.

FIG. 2( a) is a flowchart depicting an exemplary method 200 a of payment processing. In accordance with an embodiment of the present invention, the process begins 202 when the biller emails the payer a billing statement with an embedded “pay online” hyperlink 204. The payer then selects the “pay online” hyperlink 206, and the payer's token or other data is used to pre-populate the biller's custom online payment form 108 with payer information 208, which is then presented to the payer 210.

Continuing with FIG. 2( b), in an embodiment of the invention, the payer next reviews the pre-populated data and provides information for payment, such as credit card, debit card or banking account information 214. If the payer has previously used the system with the biller, and if the payer has authorized the biller to retain payment information, the payment information may already be pre-populated on the payment form 108, in which case the payer needs only to review the information and authorize payment.

In addition, in an embodiment of the invention, the payer is presented with an option to specify saving payment data to a secure hosted server for future transactions 216. In another embodiment, the payer is presented with an option to authorize automatic recurring payment for future charges 218.

In one embodiment of the invention, the biller is provided with an option to request that email notices of payments be sent to the biller's organizational contact 220 and/or the payer's email address.

FIG. 3 is a flowchart 300 depicting an exemplary method of payment processing including optional authorization of saving payment data. In accordance with an embodiment of the present invention, the method begins 301 when the payer authorizes the saving of payment data to a secure hosted server for future transactions 302. Next, a token that is logically associated with payer's account data is generated and sent to the secure form server 110 for downloads to biller's accounting system, and future use.

Subsequently, the next time the payer selects the “pay online” hyperlink for the biller, the biller's online payment form is populated with the payer's data, including the payer's payment data 306.

FIG. 4( a) is a flowchart depicting an exemplary method of payment processing including provision of email payment notices. In accordance with an embodiment of the present invention, the method starts 401 when the biller requests that email notices of payments be sent to the biller's organizational contact 402. This request may be made by various means, such as by an input field on the payment form 108, by an input field on another biller-provided form or web page, by prior agreement such as a contract, or by any other means, without limitation.

After the payer completes payment the email notice(s) are emailed to the biller's organizational contact and payer's email 404.

FIG. 4( b) is a flowchart depicting an exemplary method of payment processing including downloading of completed transaction records by a biller's organizational contact. In accordance with an embodiment of the present invention, a biller's authorized organizational contact may log into the secure server and download all or specific payers' completed transaction records. In an embodiment of the invention the transaction records include the payer's “token”, as well as data such as a passed general ledger accounting code.

The following is an example of a system embodying some aspects of the present invention, Click-to-pay™. It is described herein for illustrative purposes only.

Click-to-pay™ provides a “smart” pay online link in billing statements that are emailed to customers. The pay online link includes a personalized URL which includes a token and/or other data that uniquely identifies the payer. The link takes the payer to the organization's customized online payment form and transmits the token and other data to the payment form so that stored information about the payer can be used to pre-populate fields such as name, address, payment amount, etc. This method can also be used to pass other data such as the appropriate general ledger or accounting code to associate with the payment transaction.

With all or most of the payer's data pre-populated onto the payment form, the payer needs only to review that the data is correct and enter the data for the credit card or other method of payment. Even the need to enter the credit card or bank account data can be eliminated via Click-to-pay™'s option to save the account data to a hosted secure server for use in future transactions. In addition, once payers elect to save the account data, the Click-to-pay™ payment form can be configured to offer the payer the option to authorize automatic recurring payment for future charges.

Click-to-pay™ also provides optional email notices to the biller and/or payer when payments have been completed. The organization's billing coordinator can log-in to the secure server to review all competed transactions and approve them for download. The download process is customized to create a file that is appropriately formatted for updating the organizations accounting system.

Although the invention herein has been described with reference to particular embodiments, it is to be understood that these embodiments are merely illustrative of the principles and applications of the present invention. It is therefore to be understood that numerous modifications may be made to the illustrative embodiments and that other arrangements may be devised without departing from the spirit and scope of the present invention as defined by the appended claims. 

1. A payment processing method comprising: emailing a billing statement to a payer by a biller, the billing statement comprising an online payment hyperlink, the online payment hyperlink comprising a URL personalized for the payer and a token uniquely identifying the payer; selecting the online payment hyperlink by the payer; presenting the payer with the biller's online payment form, the online payment form comprising data fields pre-populated with available payer information; reviewing the biller's online payment form by the payer; completing and correcting data in the online payment form as needed by the payer; and sending the completed online payment form to a secure payment form server by the payer.
 2. The payment processing method according to claim 1, further comprising transmitting payer payment data to an online payment gateway by the secure payment form server; processing payment by the online payment gateway.
 3. The payment processing method according to claim 2, wherein processing payment by the online payment gateway comprises accessing a secure data vault to obtain payer payment information; transmitting payer payment information to a credit/debit card or alternative payment network; receiving a transaction record from the credit/debit card network; updating the secure data vault with the transaction record information; and updating payer's available payer information.
 4. The payment processing method according to claim 1, further comprising presenting the payer an option to authorize saving payment data to a hosted secure server; authorizing saving of payment data to the hosted secure server by the payer; and saving payment data by a hosted secure server.
 5. The payment processing method according to claim 1, further comprising presenting the payer an option to authorize automatic recurring payments to the biller; and authorizing automatic recurring payments to the biller by the payer.
 6. The payment processing method according to claim 5, further comprising recording an electronic signature of authorization from the payer.
 7. The payment processing method according to claim 1, further comprising authorizing payment notices to a biller's organizational contact by the biller.
 8. The payment processing method according to claim 7, further comprising sending an email notice to biller's organizational contact upon payment completion.
 9. The payment processing method according to claim 7, further comprising logging into the hosted secure server by the biller's organizational contact; and downloading payers' completed transaction records by the biller's organizational contact.
 10. A payment processing system comprising: a billing statement emailed to a payer by a biller, the billing statement comprising a online payment hyperlink, the online payment hyperlink comprising a URL personalized for the payer, which directs the payer to an organization's hosted payment form, and further comprises a token uniquely identifying the payer, wherein the online payment hyperlink is selected by the payer; and a biller's online payment form is presented to the payer, the online payment form comprising data fields pre-populated with available payer information, the payer reviewing the biller's online payment form, completing and correcting data in the online payment form as needed, and sending the completed online payment form to a secure payment form server.
 11. The payment processing system according to claim 10, further comprising an online payment gateway, wherein payer payment data is transmitted to the online payment gateway by the secure payment form server, and payment is processed by the online payment gateway.
 12. The payment processing system according to claim 11, wherein processing payment by the online payment gateway further comprises accessing a secure data vault to obtain payer account information; transmitting payer payment information to a credit/debit card network or other payment network; receiving a transaction record from the credit/debit card network or other payment network; updating the secure form server with the transaction record information; and updating the secure data vault with the payer's available account information.
 13. The payment processing system according to claim 10, further comprising presenting the payer an option to authorize saving payment data to a hosted secure server; authorizing saving of payment data to the hosted secure server by the payer; and saving payment data by a hosted secure server.
 14. The payment processing system according to claim 10, further comprising presenting the payer an option to authorize automatic recurring payments to the biller; and authorizing automatic recurring payments to the biller by the payer.
 15. The payment processing system according to claim 10, further comprising presenting the biller an option to have email payment notices generated to a biller's organizational contact; and authorizing payment notices to the payer.
 16. The payment processing system according to claim 15, further comprising sending an email notice to biller's organizational contact and payer upon payment completion.
 17. The payment processing system according to claim 15, further comprising logging into the hosted secure server by the biller's organizational contact; and downloading completed transaction records and tokens by the biller's organizational contact.
 18. The payment processing system according to claim 10, wherein the online payment hyperlink further comprises data to facilitate accounting for payer payment.
 19. A payment processing system comprising: a billing statement emailed to a payer by a biller, the billing statement comprising a online payment hyperlink, the online payment hyperlink comprising a URL personalized for the payer, which directs the payer to an organizations hosted payment form, and further comprises a token uniquely identifying the payer, wherein the online payment hyperlink is selected by the payer; a biller's online payment form is presented to the payer, the online payment form comprising data fields pre-populated with available payer information, the payer reviewing the biller's online payment form, completing and correcting data in the online payment form as needed, and sending the completed online payment form to a secure payment form server; an online payment gateway, wherein payer payment data is transmitted to the online payment gateway by the secure payment form server, and payment is processed by the online payment gateway, wherein processing payment by the online payment gateway further comprises accessing a secure data vault to obtain payer account information; transmitting payer payment information to a credit/debit card network or other payment network; receiving a transaction record from the credit/debit card network or other payment network; updating the secure form server with the transaction record information; and updating the secure data vault with the payer's available account information. 